Export Settings Page

The first step is to select the CData Virtuality Server objects that should be exported. On this page you can select the following objects to be exported:

• Data sources: there are two ways to export data sources. One is to use createDatasource/Connection statements, and the other is to use the importDatasource/Connection statements.

  When importing the script, createDatasource/Connection procedures perform validation, while importDatasource/Connection procedures don't.

  By default, the export wizard exports data sources using import statements, so they can be imported even if a particular data source is unreachable at the moment of import. This is a common approach used to set up the server outside the production environment first.

  To force validation on import, simply uncheck the Do not validate data sources on import option.

• Virtual schemas: there is also an option to export virtual views and procedures using fail-safe statements. If the option Do not validate views and procedures on import is not checked, virtual view and procedure definitions are printed directly to the export script. Therefore, the CData Virtuality Server will perform validation on import. The export script will arrange views and procedures in the proper creation order, but it's still useful to disable validation, especially when there are complex dependencies between procedures and views. In this case, definitions are wrapped into fail-safe importView/Procedure statements.
• Optimizations: the following options are available:
  • Export the recommended indexes: include recommended indexes in the export.
  • Do not validate views and procedures on import: similar to virtual views and data sources, determines whether to use fail-safe procedures to import/create optimizations. Please note, a fail-safe import retains optimization mat-table prefixes and should be used with care. If the destination server already has some optimizations, it is highly recommended to enable optimization validation on import. Using fail-safe statements is very useful for data backup/restore.
  • Export the states and properties of materialized tables: if optimization validation is disabled, and thus optimization materialized table prefixes are retained, it is possible to export materialized table information. Please note, this option can be used only when importing a script to a CData Virtuality Server that uses the same Analytical Storage data source.
• Jobs and schedules. Note, if a particular optimization is not selected, the corresponding jobs will be disabled.
• Users and roles. Note, if at least one of a user's roles is not selected, the user will be disabled. Users having no roles are also disabled. All the passwords are encrypted.
• Permissions. By default, permissions are automatically exported for all the selected roles. This is the most common use-case to backup the users list with all the roles and role permissions or to transfer roles/users to another installation of CData Virtuality Server. However, there are use-cases where permissions for the roles should be exported separately, i.e., when permissions already exist on the target server. This tab allows to take control over the permission export by selecting the "Export permissions separately from roles" option.
• Options. Only options configurable via setDefaultOptionValue procedure are exported. Options are not exported if no value has been set. Note, that options values are effective immediately and many impact the overall CData Virtuality Server performance (e.g. MAINTENANCE option would change maintenance mode setting)
• System properties. User-defined system properties.
• SMTP configuration. When checked, the SMTP-server host, port, SSL and STARTTLS settings are exported as well as authentication details. If configured, the password is exported encrypted.
• SSH Tunnels. If configured, all passwords (remote host password, proxy password) are exported encrypted.
• Attributes. Attributes configured for Web Business Data Shop (e.g. Owner) items. Please, note that the items should be present. Attributes would not be created for items that are not present in the target system. The import script would not fail if the items are not present.
• Web Business Data Shop. Items published to Web Business Data Shop. Please, note that the items should be present. The import script would not fail if the items are not present.

Next Step

Click Next to define a destination for the generated script.